chore(release): 0.6.2#33
Merged
Merged
Conversation
Roll the unreleased Grafana integration, documentation/onboarding overhaul (EN + VI), and Debian packaging hygiene into a tagged release. No daemon code changes — the binary is identical to 0.6.1; this is a patch under the project's convention (minor = new daemon capability/milestone or breaking change; patch = fixes, docs, integrations, packaging). Bumps all four version sources in lockstep so the release-packages verify-versions gate passes (tag v0.6.2 == meson == debian/changelog == spec): - meson.build: 0.6.1 -> 0.6.2 - debian/changelog: new 0.6.2-1 entry - pamsignal.spec: Version 0.6.1 -> 0.6.2 - CHANGELOG.md: roll ## Unreleased -> ## 0.6.2 Note: pamsignal.spec %changelog is stale (top entry 0.4.0; 0.5.0/0.6.0/0.6.1 were never backfilled). Left as-is to match existing practice — bumping the Version field is all the release gate requires; backfilling is separate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.6.2
Rolls the accumulated
## Unreleasedwork into a tagged patch release. No daemon code changes — the binary is byte-identical to 0.6.1, so this is a patch under your convention (minor = new daemon capability/milestone or breaking change; patch = fixes, docs, integrations, packaging — consistent with 0.6.1 and 0.4.1).What ships in 0.6.2
examples/grafana/(Alloy config, 12-panel fleet dashboard, 4 alert rules, docker-compose try-it stack,verify.sh) + the design doc.debian/watch,debian/upstream/metadata,Standards-Version4.7.0.Version lockstep (so
verify-versionspasses)All four sources now agree on
0.6.2— the release-packages gate checks tag == meson ==debian/changelogupstream == spec:meson.build0.6.2debian/changelog0.6.2-1pamsignal.specVersion: 0.6.2CHANGELOG.md## 0.6.2 — 2026-06-03Heads-up
pamsignal.spec's%changelogis stale (top entry0.4.0; 0.5.0/0.6.0/0.6.1 were never backfilled). I left it as-is — the gate only reads theVersion:field, and adding a lone 0.6.2 entry over that gap would be misleading. Backfilling the spec changelog is a separate cleanup if you want it.release-packages.ymltriggers onrelease: published, not on a bare tag. So the sequence is:main.v0.6.2(targetingmain) → CI runsverify-versions, builds + tests the .deb (noble + focal) and .rpm (fedora + el9), GPG-signs them, attaches them to the release, and publishes the signed apt + dnf repos to gh-pages.I'll create that release once you've merged + are happy with the notes (it's the public-publish trigger, so I'll wait for your go).
🤖 Generated with Claude Code